forked from elizaOS/eliza
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/v2/telegram #56
Open
jmikedupont2
wants to merge
79
commits into
feature/v2/groq
Choose a base branch
from
feature/v2/telegram
base: feature/v2/groq
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fixed add plugin command quickstart.md
fixed add plugin command quickstart.md
3786456
to
a713372
Compare
…update-to-send-only-changed-fields feat: add partial agent update
…chatid-uuid fix: tg negative id
feat: show client on received messages memory
…ption chore: encrypt character secrets from GUI
feat: salt agent secrets
73c1307
to
85350a1
Compare
fix: cli related
change default director for models and cache for localai
68e7fe0
to
6baa4d9
Compare
remove onclick improve gh access token instructions, include link improve plugin name handling provide clear instruction to install plugin with bun fix remove-plugin little spelling fixes fix remove-plugin so it runs rm -rf fix post create plugin instructions Add shouldRespondOnlyToMentions option for discord add missing dep Fix Tailwind typos "flex-column" -> "flex-col"; fix excessive gap on msg list. prevent message overlap clean code env api env ui add envs use active tab state update local/global env works disable button when updating force PUT always fixed jsdoc-automation.yml and removed environment.test.ts Refactored SOL address handling in plugin-solana actions to use environment variables since no settings exported, and Solve the problem of the isTransferContent judgment logic. enable settings nav button null check allow character(s) loading
8e94c8f
to
5e8a26e
Compare
import * as Groq from '@elizaos/plugin-groq'; | ||
import * as Discord from '@elizaos/plugin-discord'; | ||
import * as Twitter from '@elizaos/plugin-twitter'; | ||
import * as Telgram from '@elizaos/plugin-telegram'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a typo in the import statement for the Telegram plugin. It should be 'Telegram' instead of 'Telgram', which could lead to runtime errors when trying to use this plugin.
Pull request summary
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relates to
Risks
Background
What does this PR do?
What kind of change is this?
Documentation changes needed?
Testing
Where should a reviewer start?
Detailed testing steps